-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post 2.6.0 release update for changelog and compatibility #564
Conversation
Signed-off-by: Vacha Shah <[email protected]>
b21f5a1
to
e2a864f
Compare
Signed-off-by: Daniel (dB.) Doubrovkine <[email protected]>
Can we include CHANGELOG changes as a preparation for the release for next time? Maybe somewhere in instructions? |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-564-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ddff6cec9b475c9130516f83569ddb214d203dbe
# Push it to GitHub
git push --set-upstream origin backport/backport-564-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x Then, create a pull request where the |
Sure! I will add them in the instructions. |
@VachaShah we need to backport to |
Description
Describe what this change achieves.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.